home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
system
/
eu1_00.zip
/
ES.MAN
< prev
next >
Wrap
Text File
|
1980-01-01
|
3KB
|
83 lines
Eldar Utilities Ver.1.00
Execution Statistics
(C) Eldar Software, 1991
The ES (Execution Statistics) component gives you a possibility
to control what programs are executed often. It is necessary if you
would like to optimize disk allocation using Compress from PCTools package
or similar software. It is also very useful if you want to know what files
are most probable would be the object of a virus attack to check them
properly. Many programs exist which allow to control checksums and integrity
of selected file, e.g. FC (File Control), EC (Executable-file control)
from our AntiVirus system Cassandra. It is rational to place such program
in AUTOEXEC.BAT to control most probable victims of infection, but
how to determine them ? This problem is decided by ES.
ES consists of two part. First of them, ES itself, is a
resident monitor which is keeping in file names of all programs loaded
for execution. It is rational to insert it into the AUTOEXEC.BAT.
The only parameter for ES is file name.
!!! Note that you should specify full file name including drive
and full path !
Another part, Execution Statistics Processor (ESP) reads this file
and merges it with the results of its previous work, so the results are
accumulated. This component is also rational to place in AUTOEXEC.BAT.
ESP has two parameters: first is the file created by ES, it becomes
empty after the processing, second parameter is the file with accumulated
data. On the first run this file created. In this file you'll see
the list of programs with counts. Counts take first 5 bytes. Programs
listed there in alphabetical order but you could use ordinary SORT
command to sort list by the quantity of calls using the next command:
SORT /r <your-file >new-file
Most suitable way to use ES is to include in AUTOEXEC.BAT
two strings:
ESP c:\sys\log c:\sys\stat
ES c:\sys\log
Here it is supposed that c: is your system hard drive and
there is a directory SYS for some system purposes. After that you'll
have in C:\SYS\STAT frequnces of the program loadings. That ones which
are loaded often are the subject to control and optimize.
See the example, that is a part ofsuch table sorted using
SORT command:
00463 C:\COMMAND.COM
...
00047 C:\LINK\DEBUG.COM
00038 C:\MASM\LINK.EXE
00035 C:\MASM\EXE2BIN.EXE
00022 C:\LINK\UC.COM
...
00013 TR.COM
00010 TEST.EXE
00004 CASS.EXE
...
00004 C:\LINK\SGN.EXE
00004 C:\DOS\DISKCOPY.COM
00003 C:\LINK\UUE.COM
00003 C:\LINK\RCD.EXE
00001 C:\LINK\BOOTID.EXE
First group contains the very high usable programs. Really
command.com loads itself after every big program, so the quantity
of loadings is high. This group will includes overlays of the command
shells, you are using. It can be also NCMAIN.EXE, WPVIEW.EXE for
Norton Commander etc. This group is highly recommended to be controlled
during every rebooting. Next group consists of the popular packages
and can be controlled once a day, when turned on first time.
Next group has no path because that is the debugged programs.
There is no necessaty to control them of course. The same is right
also for the last group of programs which are used episodically,
though it is useful to keep their control sums etc. to have the
possibility to check them if needed.